@vcunat @lovesegfault I can build on this branch pkgs.hello now, but some of the changes are slightly messy. So before I continue here, I'd have two requests:

• It would be nice to get some feedback to the current changes I made (I tried to document the reasons in the corresponding commit messages)
• It would help if https://hydra.nixos.org/jobset/nixpkgs/glibc-2.33 could be reconfigured to be re-used for glibc-2.34.

Thanks! :)

Does this require the binutils update?

Doesn't seem as if that's the case currently :)

I'm not sure if it's good to test them separately and then merge without testing those two updates together.

Quick look: the bootstrapping change is OK-ish, I think. The rest seems good.

I'm not sure why diffutils update was included. Nit: 2.33-master.patch.gz should be deleted.

I'm not sure if it's good to test them separately and then merge without testing those two updates together.

I haven't taken a close look at bintuils, but considering that I even had to do some workarounds to get gcc building (yay, compatibility), I guess this will take a while (no idea if it'll land in 21.11), so it's rather likely that this will be here for a while after a git pull upstream staging --rebase for a while :)

Quick look: the bootstrapping change is OK-ish, I think. The rest seems good.

OK, great! :)

I'm not sure why diffutils update was included

With this change, the package compiled again (but good point, should perhaps add a note to the commit message).

Nit: 2.33-master.patch.gz should be deleted

Oh, good point :)

I cancelled these builds for now, as too much work is piling up. (also PR #135611)

@vcunat Hydra's queue status currently says Queue (117/125309). I have to admit that I don't really know the average and I didn't follow the current state of what's going on (with openssl I guess?) very closely (exam phase ^^), but I assume I should wait a few days before starting a new eval? :)

Yes, most of 21.05 jobs still don't have binaries with the new openssl. And then there's lots of stuff that was cancelled and will also want to continue after this settles, e.g. the current staging-next.

fetchpatchable patch for catch 1.x: https://src.fedoraproject.org/rpms/catch1/blob/059104ba87494c0b5ebe16844ec190f253e51cac/f/catch1-sigstksz.patch

@jonringer would you mind restarting hte aborted jobs in https://hydra.jonringer.us/eval/551 ? :)

Sorry I just say this now. Restarted

TIL to build my entire workstation's NixOS from source, I need a c6a.32xlarge from AWS and ~90GB of free disk space. In other words, I'm currently writing this comment from a NixOS using glibc 2.34.

Since that's also working perfectly fine, I'd say that this PR has reached a reasonably stable state. @jonringer I guess it'd make sense to cancel the jobset again and start a new eval with the current state.

As soon as everything else is sorted out, I'd be fine with merging :)

I think we can get the remaining regressions in staging-next. The next round should probably be dedicated to glibc, then the round after for systemd 250.

cc @NixOS/nixos-release-managers

So the recent hydra.nixos.org evaluation of this should be cancelled? I can't see why it's building on both farms at once.

I think that was on oversight of mine, cancelled on hydra.nixos.org, sorry!

I think stdenv changes were not completely rolled back. Noticed as a bootstrap failure on glibc-2.35. Proposed the fix as #162197

fyi the stdenv is still building fine for me, ut I guess that there's another GCC to be built, so this should be merged, but it's not a blocker.

also, does that mean you're working on glibc-2.35? :)

(in that case the next mass-rebuild project for me would be a GCC major bump %))

I run glibc-2.35 only locally to have a fresh upstream release. I don't think i'll be able to get all of nixpkgs to 2.35. I can only provide one-off fixes for packages I use.